Description

Introduces alarms for anomolous event volumes

Context

Each Notify bounded context (microservice) is deployed independently, on its own cadence, but communicates via a shared event bus using publish / subscribe patterns.

This creates an inherent systemic risk:

A change in one service may unintentionally reduce or stop event publishing
A subscriber may stop consuming events due to code, config, or dependency changes
These failures may not trigger errors (e.g. no DLQ growth, no hard failures)

Type of changes

• Refactoring (non-breaking change)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would change existing functionality)
• Bug fix (non-breaking change which fixes an issue)

Checklist

• I am familiar with the contributing guidelines
• I have followed the code style of the project
• I have added tests to cover my changes
• I have updated the documentation accordingly
• This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

• I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.